-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Switch packages to use the @nx scope #16069
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 1 Ignored Deployment
|
Deployment failed with the following error:
|
FrozenPandaz
force-pushed
the
nx-scope
branch
3 times, most recently
from
April 4, 2023 14:49
10004e0
to
2fe0f79
Compare
This pull request has already been merged/closed. If you experience issues related to these changes, please open a new issue referencing this pull request. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Switch packages to use the @nx scope
Nx's first party plugins and other packages will be published under
@nx
starting in v16.@nrwl/*
packages will no longer be published in Nx 17.This PR does the following:
@nrwl/
packages are now published under the@nx
scope.@nrwl/js
=>@nx/js
@nrwl/react
=>@nx/react
@nrwl/angular
=>@nx/angular
@nrwl/tao
which does not need to be changed to@nx/tao
but needs to collect consistent statistics.@nrwl/*
packages are still published but they are shells of their@nx/
counterparts@nx
counterparts@nrwl/react:library
)@nrwl/webpack:webpack
)README.md
which says that the package has been deprecated and to use the@nx/*
counterpart@nrwl/*
packages should be able to be done the same way in Nx 16@nrwl/*
packages will cease to be published@nx
packages have been added to the package group@nx
packages have replaced the@nrwl
packages in the First party plugins fornx list
@nx/*
imports@nrwl/
create-nx-workspace
will still install@nrwl/
@nrwl/*
packages are working properly.@nx
@nx/*
packages as@nrwl/*
docsMisc changes that were necessary to make this possible:
@nx/angular
is now built with@nx/angular:package
instead of@angular-devkit/build-angular:ng-packagr
@nrwl/jest:jest
references@nx/jest:jest
for its implementationexecutors
like you cangenerators
because it makes less sense forexecutors
.Current Behavior
Packages are published under the
@nrwl
scope.Expected Behavior
Packages are published under the
@nx
scope.We will still publish
@nrwl/
packages for v17 but they will be wrappers of their@nx
counterparts.We plan to stop publishing
@nrwl/
packages starting in v18.There is a migration to help people automatically move to the
@nx
packages.Related Issue(s)
Fixes #